ci: use the next channel - #2
Merged
Merged
Conversation
The edge and edge-next channels were renamed to next. Every matrix leg here still pointed at the old names, so these builds resolve a feed that no longer exists. Retarget them; the release stays as it is.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
edgeandedge-nextchannels were renamed tonext. Every matrix leg in this repo still pointed at the old names, so these builds resolve a package feed that no longer exists.This retargets them to
nextand changes nothing else — the distro release stays as it was.Note the
2026/nextleg inrelease.ymlonly runs on a version tag, and the 2026 feed currently publishes onlyjetson-agx-thor, so that leg will not succeed until this target lands there.